| 1. | Prevents non - repeatable reads but phantom rows are still possible 防止不可重复的读取,但是仍可以有幻像行。 |
| 2. | This leaves you a choice between read committed and repeatable read 剩下的也就是在“授权读取”和“可重复读取”之间选择了。 |
| 3. | Repeatable read - rr 可重复读rr |
| 4. | Non repeatable read 不可重复读 |
| 5. | By default , mysql uses the repeatable read isolation level for all transactions 默认情况下, mysql对所有事务使用repeatable read隔离级别。 |
| 6. | Incorrect concurrency can lead to problems such as dirty reads , phantom reads , and non - repeatable reads 不正确的并发可能导致脏读、幻读和不可重复读等问题。 |
| 7. | This is an important issue , but using repeatable read isn ' t the only way to resolve it 这是一个非常重要的问题,但是使用可重复读取并不是解决问题的唯一途径。 |
| 8. | For example , reading from a read - only look up table doesn t require repeatable read , and uncommitted read is sufficient 比如,读取只读的查找表不需要可重复读级别,未提交读级别就足够了。 |
| 9. | Readpast can only be specified in transactions operating at the read committed or repeatable read isolation levels 仅可在运行于read committed或repeatable read隔离级别的事务中指定readpast 。 |
| 10. | Specifies that a scan is performed with the same locking semantics as a transaction running at repeatable read isolation level 指定事务在repeatable read隔离级别运行时,使用相同的锁定语义执行一次扫描。 |